Why a CMMI Level 5 Company Fails to Meet the Deadlines?
نویسندگان
چکیده
Reliable effort and cost estimation remains to be a challenging issue even for mature software organizations. Although, these organizations collect historical data to base their future estimates, changes in circumstances (such as application type, development platform, etc.) prevent their successful utilization. As a result, companies often suffer from underestimated and unrealistic schedules. Managing software projects that involve a large number of globally distributed stakeholders makes estimation and planning even more challenging. Related studies show that even knowledgeable project managers often underestimate hidden costs and sources of delay associated with distributed development. Therefore, management activities such as estimation of development effort, planning and control require special attention. In this paper we discuss experiences gained from a highly distributed software project, which aimed at development of a product based on a new platform and architectural solution. The project was conducted in a CMMI Level 5 company and still failed to meet initial plan constraints. We thus provide an overview of management decisions in the light of their consequences, and discuss potential areas of improvement.
منابع مشابه
Reengineering the Industrial CMMI
Abstract of Re-engineering of Industrial CMMI Through this research, I have established a general strategy to appraise an organization against a scale of five process maturity levels whilst maintaining a strong mechanics of CMMI. Reengineering of industrial CMMI proposes a novel method for Industrial Competence ranking of those organizations/companies which are targeting various CMM...
متن کاملScrum and CMMI – Going from Good to Great Are you ready-ready to be done-done?
Projects combining agile methods with CMMI combine adaptability with predictability to better serve large customer needs. The introduction of Scrum at Systematic, a CMMI Level 5 company, doubled productivity and cut defects by 40% compared to waterfall projects in 2006 by focusing on early testing and time to fix builds. Systematic institutionalized Scrum across all projects and used data drive...
متن کاملWhat Can Be Learned from CMMi Failures?
The software crisis has been around since 1968 when NATO first identified the problematic nature of software development. In recognition of the need to manage the process of software development many methodologies have been proposed over the years. A recent contribution to this rich set of rigorous software development methodologies is the Software Engineering Institute’s (SEI) Capability Matur...
متن کاملImplementing CMMI using a Combination of Agile Methods
This paper explores the possibility for software companies of getting a CMMI certification of their processes by applying agile practices. For this purpose, starting with CMMI maturity level 2 generic goals and practices, we analyze the applicability of a series of agile methods, identifying their individual or combined contribution in the fulfillment of each process area. The main result of th...
متن کاملThe Influence of CMMI on Establishing an Architecting Process
A large IT company is creating a generic architecting process. Since the company has set an objective to achieve Maturity Level 3 of the Capability Maturity Model Integration (CMMI), the process needs to comply with the relevant requirements set by the CMMI. This paper presents the elicitation of such requirements, and the resulting set of requirements. It analyzes their potential impact on gen...
متن کامل